Release Notes
The notes below provide descriptions of the new features and changes introduced with each release of Eggplant DAI. You are strongly encouraged to read about the relevant changes whenever you upgrade from an earlier version.
Potential compatibility issues are highlighted.
System Requirements
Operating Systems
- Windows: Windows Server 2019 or 2022 is recommended for production use but Windows 10 and 11 are also supported.
Hardware Requirements
- RAM: 8 GB minimum
- Disk Space: 5 GB minimum for trial deployments, 100 GB minimum for production deployments
- Processor: 64-bit Intel Core 2.3 GHz or equivalent (4+ cores or 8+ threads recommended)
- Eggplant DAI 7.0 is the latest supported release.
- You must upgrade to Eggplant DAI 6.5 before you start your installation.
- Before you upgrade, make sure that you take a backup of your files and database. If there is a problem with your upgrade, you will need to restore to this point.
- The upgrade may take 5-10 minutes to complete.
- Eggplant DAI 7.0 is only compatible with Eggplant Functional 23.0 and later. When upgrading to Eggplant DAI 7.0, you must also update your version of Eggplant Functional.
- The DAI Agent has been split into two agents; Design Agent and Run Agent. You will need to install both agents.
Release 7.0 (July 2023)
MinIO deployment upgrade
An upgrade has been made to the latest stable release of MinIO. Upgrading an existing installation of DAI 6.5 to DAI 7.0 will bring about a migration of MinIO assets(mainly suites and screenshots) which may take up to an hour.
Agent redesigned
The agent has been redesigned into separate dedicated agents for design and run. There are two types of agents, namely DAI Design Agent for uploading suites to DAI and executing tests in the designer, and DAI Run Agent for executing test configuration runs. Both agents are required.
[Windows Only] From version 7.0.0-0 onwards, if you have an older agent installed i.e. eggplantAIagent
, it will be removed during the installation of either the newer DAI Design Agent or the newer DAI Run Agent.
Execution Environment List
On the SUTs page, you no longer need to type the Execution Environment name that will be used by a SUT. You can now pick your Execution Environment from a list of Execution Environments that can also be filtered. You may also leave the Execution Environment field blank except for connections to Android and iOS devices.
SUT connection configuration
Made it easier for you to avoid misconfiguring your connections. If RDP or VNC are the primary connections, then only Webdriver will be available as secondary connection and vice versa. There can only be one connection if Citrix, Sauce Labs Browser, Sauce Labs Browser, Android Device or iOS Device is selected.
Email notification by test result type
Choose to receive email notification based on the type of test result; Pass, Fail, Error, Cancelled. By default all options are selected on creation of a test configuration.
Single Sign-On (ADFS with OIDC)
Single Sign-On functionality for DAI will enable our users who use Active Directory configured over the OIDC protocol to control their users' access in a unified way. If you’re interested in learning more, please reach out to your Account Manager who can assist.
Source code management integration - GIT
Support for GIT Integration has been added. This makes it possible for test runs to use scripts from GIT repositories. Does not support SVN.
Natively connect to Android and iOS devices
This option is available in the SUT connection type list. Your device will connect through the Eggplant Gateway.
Filtering on test result page
Filtering by suite added in test result page.
Security updates
A number of security enhancements have been made to DAI 7.0, including the latest stable release of MinIO.
Known Issues
When upgrading from DAI 6.5 you may need to manually end a process to allow the install to proceed, see Upgrading from DAI 6.5 for details.
Release 6.5
Test Case result trend
DAI provides a result trend of the last ten test runs in the test case view. This is an overview of test runs that have completed successfully or failed. The result trend will enable you to understand how well your test runs are performing. The trend also shows when the test was run and its duration.
Support for Citrix
Added native support for Citrix Desktop connections
Support for Sauce Lab Devices
Added native support for Sauce Labs Browser and Sauce Labs Real Devices (private and Public) in DAI.
Automatic Cleanup of DAI server logs
DAI can be set to automatically delete DAI server log files.
Release 6.4
Test Results by Email
You can now receive notification of your test results by email. The results will show whether a test has been successful or not. Email notification will allow you to take prompt action and save you from having to constantly log into DAI to check the status of your test configuration runs.
Calendar View for Scheduling Test runs
The new calendar provides you with full visibility of your test configuration schedules. The new calendar will facilitate optimisation of your execution environments according to availability of the environments and licenses.
Script-Based Test Cases
Test cases with a sequence of scripts are now available in this release. You can quickly and easily create test cases with your scripts in a similar way to model based testing.
All script-based steps that were referenced from within Test Configurations will be migrated to Test Cases and these will be automatically included within the original Test Configuration. New script-based tests can also be created within Test Cases. Test Configurations will hold your script-based test cases.
The above changes align DAI with how you create Models and Test Configurations for Models.
The test results for migrated script test cases will be displayed in Test Results with the relevant suite name and test configuration (type). However, the suite name and type will be missing links to their suite and test configuration respectively. You will need to manually navigate to the relevant suite or test configuration if needed.
In addition, in the test results logs, the name of the scripts that were executed will not be available. This is because test results are not associated to test steps. However, once these test cases are run again, the details of the test steps will be available in the new test results.
Visibility of Suite Contents
You can view the contents of your suites (files, images and resources) that are stored in DAI. You will also have details of the suites such as version and time when it was last updated. With this information, you can easily determine whether you are using the correct suite version.
SMTP Settings
SMTP settings are now configurable within DAI.
Security
A number of security updates have been made, including upgrades to Python (v3.11.3), Keycloak (v19.0.3) and the latest stable releases of PostgreSQL, Nginx, RabbitMQ and MinIO.
Previous versions of DAI shipped with a pre-configured Third Party Client client:dai:agent:integration
. This has now been removed to enhance security. Users can create their own Third Party Client if needed instead.
Release 6.3
Ability to edit test cases
You are now able to edit existing test cases. You can add and remove test case steps anywhere in your test case.
Test results page displays environment details
The execution environment against which your test ran is now shown in the test results page. If there are problems with the environment, the details of the environment can be more easily identified thereby facilitating troubleshooting.
Cancel test runs
Live test runs can now be canceled more easily. Navigate to the test results page, find the test run that is in progress and that you wish to cancel and cancel it at a click of a button.
Cloning of test configuration
Duplication of your test configuration is now possible. This will allow you to quickly build new test configurations.
Group Migration
An access group with the same name as the user used to get automatically created for every user up until DAI version 6.3. We now allow sharing access to models directly with users and will no longer create those user-aligned access groups. With that design decision in mind, during the 6.3 upgrade process:
- Groups not associated with any models get removed.
- True user-aligned groups with only their original user as a member get removed.
- Permissions of the removed true user-aligned groups get reassigned to their respective users.
Additionally, please note that:
- If a user-aligned group has been renamed, it will remain in the system unchanged.
- If there are multiple users in a user-aligned group, we prepend
group_
to the name. - If the original user is no longer in the group or the system, but the group is and still has models associated with it, the group will remain unchanged.